home *** CD-ROM | disk | FTP | other *** search
-
-
-
- iiiinnnnttttrrrroooo((((DDDD1111)))) iiiinnnnttttrrrroooo((((DDDD1111))))
-
-
-
- NNNNAAAAMMMMEEEE
- _iiii_nnnn_tttt_rrrr_oooo_...._DDDD_1111 - introduction to driver data
-
- SSSSYYYYNNNNOOOOPPPPSSSSIIIISSSS
- _####_iiii_nnnn_cccc_llll_uuuu_dddd_eeee _<<<<_ssss_yyyy_ssss_////_tttt_yyyy_pppp_eeee_ssss_...._hhhh_>>>>
- _####_iiii_nnnn_cccc_llll_uuuu_dddd_eeee _<<<<_ssss_yyyy_ssss_////_dddd_dddd_iiii_...._hhhh_>>>>
-
- DDDDEEEESSSSCCCCRRRRIIIIPPPPTTTTIIIIOOOONNNN
- This section describes the data definitions a developer needs to include
- in a device driver. The system finds this information in an
- implementation-specific manner, usually tied to the way system
- configuration is handled.
-
- UUUUSSSSAAAAGGGGEEEE
- Each driver is uniquely identified by a prefix string specified in its
- configuration file. The name of all the driver-supplied routines and
- global variables should begin with this prefix. This will reduce the
- chance of a symbol collision with another driver. Any private routines
- defined by a driver that are not entry point routines should be declared
- as _ssss_tttt_aaaa_tttt_iiii_cccc. Also, any global variables that are private to the driver
- should be declared as _ssss_tttt_aaaa_tttt_iiii_cccc.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- PPPPaaaaggggeeee 1111
-
-
-
-